| 翻訳と辞書 |
| Pull Up refactoring ： ウィキペディア英語版 |
Pull Up refactoring
In software engineering, Pull Up refactoring involves moving a member of a class, such as a method, from a Subclass into a Superclass.
==Application==
This refactoring is especially useful when subclasses of a certain class share some functionality but each implements it separately. Moving the shared functionality (using Extract Method if need be, or just moving the method) to the superclass will keep the functionality of the subclasses as it is, and give less code duplication and better code readability. This refactoring should not be used if only relatively few subclasses share a functionality, since this will add (probably) unintended functionality to other (most of the other ) subclasses.
Suppose we have a class A and its subclasses B, C, D, E, F and G. If B and C share a method (for example), then a better solution in this case is creating a class that will have the B and C's shared method (let's call it Z), and have B and C use the method from that class (Z in this example). That process is called Extract Class.
Another option would be making Z extend A and then making B and C extend Z.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Pull Up refactoring」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|